Method and apparatus for registering remote network devices with a control device

ABSTRACT

A method and apparatus for registering a remote network device with a control device is disclosed. In one embodiment, a registration information message is received by a bridge device from an unregistered remote network device using a first communication protocol. Identification information within the registration information message is stored in a record in a memory. A second registration information message is transmitted to the control device using the second communication protocol, the second registration information message comprising at least some of the identification information. In response, an acknowledgement message is received from the control device, the acknowledgement message comprising an identification code. When subsequent messages are received from the remote network device, the bridge associates these messages with the identification code, then re-transmits the messages to the control device using the identification code.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No.13/401,687, filed Feb. 21, 2012, now U.S. Pat. No. 9,054,892.

BACKGROUND

I. Field of Use

The present application relates to the field of digital networks. Morespecifically, the present application relates methods and apparatus forallowing disparate network nodes to communicate with each other.

II. Description of the Related Art

Home security systems have been around for years. Typically, thesesystems comprise a control unit in communication with one or more remotesensors, such as door/window sensors, motion detectors, tilt sensors,and so on. Communication between these devices may occur over one ormore wired or wireless medium, or a combination of both, forming one ormore digital networks.

A number of proprietary and open-source protocols exist that allow thevarious system components to communicate with one another. One suchprotocol that is popular today is known as the Z-wave protocol. TheZ-wave protocol assigns one device as a “controller” and other devicesas “slaves”. The controller may send commands to the slaves, requestinginformation or instructing them to perform a function. The commands sentby the controller and information sent by the slaves are sent as datapackets that are defined by the Z-wave protocol. RF transmission occursat 908 MHz

Generally, slave devices that operate using one protocol cannotcommunicate with a controller that uses a different protocol. Thislimitation may create problems for consumers who own controllers thatuse a particular communication protocol that wish to add a slave devicethat uses a different communications protocol. For example, a homeownerhaving a Z-wave-enabled controller may wish to add a driveway sensor todetect arrival and departures of vehicles to the homeowner's property.However, the driveway sensor is available using only the well-knownInsteon protocol.

Thus, it would be desirable to be able to allow slave devices using oneprotocol to communicate with a controller that uses a differentprotocol.

SUMMARY

The embodiments described herein relate to methods and apparatus forregistering a remote network device with a control device, wherein theremote network device communicates using a first communication protocoland the control device communicates using a second communicationprotocol.

In one embodiment, a method for registering a remote network device witha control device comprises receiving a registration information messageby a bridge device from a remote network device using a firstcommunication protocol, the registration information message comprisingidentification information relating to the remote network device. Inresponse, a record is created within a memory, the record for storing atleast some of the identification information. A second registrationinformation message is then transmitted to the control device using thesecond communication protocol, the second registration informationmessage comprising at least some of the identification information. Inresponse, an acknowledgement message is received from the control deviceusing the second communication protocol, the acknowledgement messagecomprising an identification code assigned by the control device, theidentification code uniquely identifying the remote network device. Theidentification code is stored in the memory, and is associated with theidentification information. Next, a subsequent message is received fromthe remote network device, and the bridge device determines whether thesubsequent message has originated from a remote network deviceassociated with the identification code. When the bridge determines thatthe subsequent message has originated from a remote network deviceassociated with the identification code, it re-transmits the subsequentmessage to the control device, the retransmitted subsequent messagecomprising the identification code.

In another embodiment, an apparatus for registering a remote networkdevice with a control device is described, wherein the remote networkdevice communicates using a first communication protocol and the controldevice communicates using a second communication protocol, comprising afirst transceiver for communicating with the remote network device usingthe first communication protocol, a second transceiver for communicatingwith the control device using the second communication protocol, aprocessor for executing processor-executable instructions, and a memoryfor storing the processor-executable instructions, theprocessor-executable instructions causing the apparatus to: receiving aregistration information message by a bridge device from a remotenetwork device using a first communication protocol, the registrationinformation message comprising identification information relating tothe remote network device. In response, a record is created within amemory, the record for storing at least some of the identificationinformation. A second registration information message is thentransmitted to the control device using the second communicationprotocol, the second registration information message comprising atleast some of the identification information. In response, anacknowledgement message is received from the control device using thesecond communication protocol, the acknowledgement message comprising anidentification code assigned by the control device, the identificationcode uniquely identifying the remote network device. The identificationcode is stored in the memory, and is associated with the identificationinformation. Next, a subsequent message is received from the remotenetwork device, comprising the identification information. In response,at least some of the identification information associated with theidentification code is used to transmit the subsequent message to theremote network device using at least some of the identificationinformation to address the remote network device. Next, a subsequentmessage is received from the remote network device, and the bridgedevice determines whether the subsequent message has originated from aremote network device associated with the identification code. When thebridge determines that the subsequent message has originated from aremote network device associated with the identification code, itre-transmits the subsequent message to the control device, theretransmitted subsequent message comprising the identification code.

BRIEF DESCRIPTION OF THE DRAWINGS

The features, advantages, and objects of the present invention willbecome more apparent from the detailed description as set forth below,when taken in conjunction with the drawings in which like referencedcharacters identify correspondingly throughout, and wherein:

FIG. 1 illustrates prior art home security system comprising a controldevice and three remote network devices;

FIG. 2 illustrates a security and/or automation system comprising acontrol device, a bridge device, and three remote network devices;

FIG. 3 is a functional block diagram of one embodiment of the bridgedevice shown in FIG. 2;

FIGS. 4a and 4b are flow diagrams illustrating one embodiment of amethod for allowing a remote network device such as the ones shown inFIG. 2 to register with the control device shown in FIG. 2 when thecontrol device and the remote network device operate using disparatecommunication protocols; and

FIGS. 5a-5c are flow diagrams illustrating another embodiment of amethod for allowing a remote network device such as the ones shown inFIG. 2 to register with the control device shown in FIG. 2 when thecontrol device and the remote network device operate using disparatecommunication protocols.

DETAILED DESCRIPTION

The present description relates to a bridge device for allowingcommunications between network nodes that use different communicationprotocols. In one embodiment, methods and apparatus are described thatallow “slave” devices to register with a “control” device. In anotherembodiment, methods and apparatus are described that allowcommunications between such slave devices and the control device duringnormal operation. The concepts disclosed herein generally related todigital communication networks found in security systems and homeautomation control systems.

FIG. 1 illustrates one embodiment of a simplified block diagram of aprior art home security system 100 comprising a control device 102 andremote network devices 104, 106, and 108. Although only three remotenetwork devices are shown, a greater, or fewer, number of remote networkdevices may be used in other systems.

Control device 102 comprises one of any number of commercially-availablehome automation and/or security controllers. It acts as a centralcontrol station for one or more sensors, such as remote network devices104, 106, and 108. Typically, such sensors comprise door/window sensors,tilt sensors, passive infra-red (PIR) sensors (i.e., motion sensors),video cameras, etc., and are deployed throughout residential or businessstructures on doors frames, windows frames, walls and so on. An exampleof control device 102 is a Simon XT panel sold by General ElectricCorporation of Fairfield, Conn. Control device 102 typically comprisescircuitry to wirelessly communicate with any of the remote networkdevices 104-108 using one or more common communication protocols, suchas Z-wave, Zigbee, X-10, Insteon, Wi-Fi, or others.

Typically, remote network devices are introduced to, or registered with,control device 102 so control device 102 knows the number and type ofsensors in network 100. For example, in one application, control device102 may be installed in a convenient location and powered on. Then, aremote network device, such as a door sensor, may be introduced tocontrol device 102, typically be placing both control device 102 and theremote network device into a “learn” mode of operation. The learn modeof operation allows control device 102 to determine the presence of theremote network device, and typically records information provided by theremote network device, such as a serial number that was pre-assigned tothe remote network device, a device type, an operational status of theremote network device, and/or other information. Control device 102, inturn, may store this information in an electronic memory for futurereference. Once a remote network device has registered with controldevice 102, it may then function in its intended manner. For example, adoor or window sensor may transmit a signal during detection of a changeof state, i.e., as a door or window is opened or closed.

Typically, each of the remote network devices and control device 102communicate with one another using the same communication protocol(e.g., Z-wave, Zigbee, X-10, Insteon, etc). However, some of the morepopular communication protocols are hampered by one or more problems,such as a limited communication range, low battery life, relativelyexpensive manufacturing costs, and bulky designs. In some cases, itwould be desirable to replace existing remote network devices (orintroduce new ones) that use such deficient protocols with remotenetwork devices that use a different protocol that minimizes thejust-mentioned limitations. For example, home security sensors arecurrently offered that operate in the range of 433 mHz, which allow suchsensors to have a much greater communication range and better batterylife. However, control device 102 may only be able to communicate usinga single communication protocol, so the replacement (or introduction) ofremote network devices that use a different communication protocol wouldbe useless. The introduction of a bridge device would be necessary inorder to allow communications between control device 102 and remotenetwork devices using disparate communication protocols, as explainedbelow.

FIG. 2 illustrates a security and/or automation system 200 comprising acontrol device 202, bridge device 204, and remote network devices 206,208, and 210. It should be understood that a remote network device maycomprise a bridge device. Typically, remote network devices 206, 208,and 210 comprise one or more door/window sensors, tilt sensors, passiveinfra-red (PIR) sensors (i.e., motion sensors), video cameras, etc., andare typically deployed throughout residential or business structures ondoors frames, windows frames, walls and so on.

Each of the remote network devices 202-210 use a communication protocolthat is different than the one used by control device 202. For example,control device 202 may use the popular Z-wave communication protocol,while each of remote network devices 206, 208, and 210 use an opennetwork protocol such as the Scalable Network Access Protocol (SNAP)which may be used in devices operating at a relatively high frequency,such as 433 mHz. Remote network devices designed to operate as such afrequency typically enjoy a large communication range, long batterylife, decreased manufacturing costs, and appealing aesthetic designs.

As mentioned above with respect to FIG. 1, remote network devices 206,208, and 210, in general, typically “register” with, or are introducedto, control device 202 so that control device 202 knows the number andtype of sensors in network 200. However, a direct process ofregistration between remote network devices 206, 208, and 210 cannot beaccomplished, because each of these remote network devices communicatesusing a different protocol than the one used by control device 202.Bridge 204 is used an intermediary to allow communications betweencontrol device 202 and the remote network devices, both for registrationpurposes and during “normal” operations, e.g., control device 202sending commands to the remote network devices and the network controldevices responding to the commands and/or providing status informationto control device 202.

Bridge 204 comprises circuitry to transmit and receive communicationsignals of a first communication protocol (e.g., for communications withcontrol device 202) and circuitry to transmit and receive communicationsignals of a second communication protocol (e.g., for communicationswith remote network devices). Although FIG. 2 suggests wirelesscommunications between bridge 204 and control device 202 and betweenbridge 204 and remote network devices 206, 208, and 210, in otherembodiments, bridge 204 could comprise circuitry that allows it tocommunicate over other types of communication channels, such as physicalconductors, to either control device 202, remote network devices, orboth types of devices. In another embodiment, some remote networkdevices may communicate with bridge 204 wirelessly, while otherscommunicate with bridge 204 over physical conductors. Moreover, in otherembodiments, bridge 204 may comprise circuitry that allowscommunications between two or more communication protocols used by twoor more remote network devices over two or more communication channels.

Bridge 204 is typically installed into a location in a home or businessin range of any existing or proposed remote network devices and withinthe range of control device 202. It is typically powered by householdpower, e.g., 115 VAC, 60 Hz in the United States.

FIG. 3 is a functional block diagram of one embodiment of bridge 204.Specifically, FIG. 3 shows processor 300, memory 302, user interface304, transceiver 306, and transceiver 308. It should be understood thatnot all of the functional blocks shown in FIG. 3 are required foroperation of bridge 204 (for example, transceiver 308 may not benecessary in an embodiment where a first communication protocol and asecond communication protocol operate using the same modulationtechnique), that the functional blocks may be connected to one anotherin a variety of ways, and that not all functional blocks necessary foroperation of bridge 204 are shown (such as a power supply), for purposesof clarity.

Processor 300 is configured to provide general operation of bridge 204by executing processor-executable instructions stored in memory 302, forexample, executable code. Processor 300 typically comprises a generalpurpose processor, such as an ADuC7024 analog microcontrollermanufactured by Analog Devices, Inc. of Norwood Mass., although any oneof a variety of microprocessors, microcomputers, and/or microcontrollersmay be used alternatively.

Memory 302 comprises one or more information storage devices, such asRAM, ROM, EEPROM, UVPROM, flash memory, CD, DVD, Memory Stick, SDmemory, XD memory, thumb drive, or virtually any other type ofelectronic, optical, or mechanical memory device. Memory 302 is used tostore the processor-executable instructions for operation of bridge 204as well as any information used by processor 200 during operation ofbridge 204, such as information regarding one or more remote networkdevices in system 200, parameter information, identificationinformation, status information, etc.

User interface 304 is coupled to processor 300 and allows a user tocontrol operation of bridge 204 and/or to receive information frombridge 204. User interface 304 may comprise one or more pushbuttons,switches, sensors, keypads, and/or microphones that generate electronicsignals for use by processor 300 upon initiation by a user. Userinterface 304 may additionally comprise one or more seven-segmentdisplays, a cathode ray tube (CRT), a liquid crystal display (LCD), oneor more light emitting diode displays (LEDD), one or more light emittingdiodes (LEDs), light arrays, or any other type of visual display.Further, the electronic display could alternatively or in additioncomprise an audio device, such as a speaker, for audible presentation ofinformation to a user. In one embodiment, user interface 304 comprises amulti-colored LED and a pushbutton.

Transceiver 306 comprises circuitry necessary to transmit and receivecommunication signals from bridge 204 to control device 202. Suchcircuitry is well known in the art and may comprise BlueTooth, Wi-Fi,RF, optical, or ultrasonic circuitry, among others. Alternatively, or inaddition, transceiver 306 comprises well-known circuitry to providesignals to a remote destination via wiring, such as telephone wiring,twisted pair, two-conductor pair, CAT wiring, or other type of wiring.

Transceiver 308 comprises circuitry necessary to transmit and receivecommunication signals from bridge 204 to one or more remote networkdevices. Such circuitry is well known in the art and may compriseBluetooth, Wi-Fi, RF, optical, or ultrasonic circuitry, among others.Alternatively, or in addition, transceiver 306 comprises well-knowncircuitry to provide signals to a remote destination via wiring, such astelephone wiring, twisted pair, two-conductor pair, CAT wiring, or othertype of wiring.

Bridge 204 may additionally comprise one or more other transceivers,each one designed to communicate with remote network devices usingcommunication protocols other than the one used by transceiver 306. Forexample, a third transceiver may communicate with a remote networkdevice over a third communication protocol different than the firstcommunication protocol used by remote network device 206 and differentthan the communication protocol used by control device 202. It should beunderstood that some of the components and/or software that comprisetransceiver 306, transceiver 308, and other transceivers may be commonto these transceivers. For example, transceiver 306 and transceiver 308may transmit on at a particular frequency common to both, while themessaging formats between the two communication protocols differ. Inthis case, transceiver 306 and transceiver 308 could comprise common RFelements, such as mixers, up-converters, modulators, down-converters,demodulators, and/or software to operate such elements.

FIGS. 4a and 4b are flow diagrams illustrating one embodiment of amethod 400 for allowing a remote network device to register with controldevice 202 when control device 202 and the remote network device operateusing disparate communication protocols. It should be understood that insome embodiments, not all of the steps shown in FIG. 4 are performed. Itshould also be understood that the order in which the steps are carriedout may be different in other embodiments.

At block 402, control device 202 is placed into a “learn” mode ofoperation from a “normal” mode of operation, typically by pressing oneor more pushbuttons on control device 202. Many commercially-availablecontrol devices require an initial registration of any network devicesthat are to be used in system 200, such as bridge 204 and one or moreremote network devices. In one embodiment, this registration process isknown as “inclusion”. In the “normal” mode of operation, control device202 typically monitors remote network devices for any messagestransmitted by those devices, transmits commands instructing remotenetwork devices to perform one or more operations, provides informationto users of network 200, provides information to a central monitoringsystem, etc.

In one embodiment, in response to being placed into learn mode, controldevice 202 transmits a message requesting that any device that has notbeen previously registered with control device 202 to respond to themessage. In another embodiment, the message instructs any device,registered or not, to respond to the message. In either case, themessage is transmitted using a first communication protocol.

At block 404, bridge 204 may also be placed in a “learn” mode ofoperation from a “normal” mode of operation, typically by pressing oneor more pushbuttons on bridge 204. In one embodiment, in response tobeing placed into learn mode, bridge 204 transmits at least oneregistration information message to control device 202 using the firstcommunication protocol common to both bridge 204 and control device 202,shown at block 406. The registration information message in eitherembodiment typically comprises identification information pertaining tobridge 204, such as a pre-assigned serial number, a device type (such asa basic device type, a specific device type, a generic device type,etc.), and/or a device status (e.g., open, closed, temperature, on, off,etc). The identification information may also comprise other informationas well, such as the capabilities of bridge 204, for example, whetherbridge 204 is capable of repeating messages to other network devices,whether bridge 204 is capable of continually “listening” for incomingmessages, etc.

In one embodiment, the registration information message transmitted bybridge 204 comprises a “node information frame” and the firstcommunication protocol comprises the well-known Z-wave communicationprotocol. The node information frame is part of the Z-Wave protocol andspecifies the capabilities of the remote network device, otherwisereferred to as a “node” in system 200. These capabilities may comprise apre-assigned device serial number, the device type, a nodeidentification code, a home identification code, whether the node isable to repeat frames, and/or other protocol-relevant issues. Remotenetwork devices 206-210 may also include similar information as theytransmit registration information messages, as described later herein.

When control device 202 receives the identification information frombridge 204 while in learn mode, it assigns a home identification codeand a node identification code to bridge 204, typically by creating arecord in an electronic memory within control device 202. The recordtypically comprises some or all of the identification information, alongwith the just-assigned home identification code and the nodeidentification code. The home identification code is an alpha-numericcode that identifies a particular network, such as system 200 and istypically unique to a particular home or business. Generally, networkdevices having the same house code can communicate with each other,while network devices having a different home identification code maynot. The home identification code is typically assigned by a processorinside control device 202 in conjunction with processor-executableinstructions and data stored within an electronic memory.

The node identification code is an alpha-numeric code that uniquelyidentifies each node, or device, in system 200. Remote network devices206, 208, and 210, as well as bridge 204, may be considered nodes.Control device 202 assigns a node identification code that is unique toeach device in network 200 as devices are introduced, or registered,to/with control device 202. The term “node identification code” may alsobe referred to as simply “identification code”.

In one embodiment, after control device 202 has assigned a homeidentification code and node identification code to bridge 204, anacknowledgment message is transmitted using the first communicationprotocol, informing bridge 204 of its assigned house and nodeidentification codes. In another embodiment, an acknowledgement messageis transmitted to bridge 204 using the first communication protocol, butthe house and node identification information is not sent. In yetanother embodiment, no message is transmitted to bridge 204. If such anacknowledgement message is transmitted, it is received by bridge 204 atblock 204, using the first communication protocol.

After bridge 204 has been successfully registered with control device202, an audible or visual indication may be presented to a user tosignify the registration. Typically, information regarding theregistration may be accessible to a user via a display located oncontrol device 202. For example, after a successful registration, an LEDmay be illuminated for a predetermined time period and a user may beable to view the assigned house and node identification codes associatedwith bridge 204, as well as other information, such as some or all ofthe identification information. Frequently, the user may add furtherinformation pertaining to each device registered with control device202, such as a location of a device (e.g., “front door”, “window inliving room”, “garage door”, etc). After successful device registration,control device 202 and/or bridge 204 are typically returned to a“normal” mode of operation, either automatically, after a predeterminedtime period, or by a user of system 200.

At some point later, a user of system 200 may want to register one ormore remote network devices with control device 202 that do notcommunicate using the same communication protocol as control device 202.In that case, these remote network devices register with bridge 204which, in turn, registers them with control device 202.

In one embodiment, to achieve remote network device registration, bridge204 may be placed into a third mode of operation (first mode being“normal” mode, second mode being “learn” mode described above), referredto herein as remote network device learn mode, shown at block 410. Theremote network device learn mode allows bridge 204 to receiveregistration information messages from one or more remote networkdevices so that remote network devices may be registered with bridge204. Registering with bridge 204 enables bridge 204 to properly routemessages to intended devices, as will be explained later herein.

In one embodiment, in response to being placed in the third mode ofoperation, e.g., second learn mode, bridge 204 transmits a message to,for example, remote network device 206 using a second communicationprotocol via transceiver 308, requesting that it (or any otherunregistered remote network device) to respond to the message with aregistration information request. The second communication protocol isdifferent than the first communication protocol. Upon receipt of themessage, remote network device 206 responds by transmittingidentification information to bridge 204 using the second communicationprotocol. In another embodiment, after bridge 204 is placed into thethird mode of operation, remote network device 206 is placed into a“learn” mode, where, in response, remote network device 206 transmits atleast one registration information message to bridge 204 using thesecond communication protocol, the message comprising identificationinformation related to remote network device 206. The identificationinformation transmitted by remote network device 206 in eitherembodiment typically comprises a pre-assigned serial number, a devicetype (such as a basic device type, a specific device type, a genericdevice type, etc.), and/or a device status (e.g., open, closed,temperature, on, off, etc). The identification information may alsocomprise other information as well, such as the capabilities of remotenetwork device 206, for example, whether remote network device 206 iscapable of repeating messages to other network devices, whether remotenetwork device 206 is capable of continually “listening” for incomingmessages, etc.

In one embodiment, the registration information message transmitted byremote network device 206 comprises a “node information frame”,described above.

At block 412, bridge 204 receives the registration information messagefrom remote network device 206 via transceiver 308, using the secondcommunication protocol common to bridge 204 and remote network device206.

When bridge 204 receives the identification information from remotenetwork device 206, processor 300 creates a record in memory 302, shownat block 414. The record comprises at least some of the identificationinformation in the registration information message. In addition,processor 300 may assign a reference code to remote network device 206and associate the reference code with remote network device 206, e.g.,the identification information stored in the record inside memory 302,at block 416. The reference code is used by processor 300 to identifyremote network devices that have “registered” with bridge 204, e.g.,have had a record created in memory 302. For example, the reference codemay comprise one of a series of alpha-numeric codes. For purposes ofexample, it is assumed that remote network device 206 is the firstdevice to register with bridge 204 and is assigned a reference codeequal to “1”.

At block 418, bridge 204 may transmit an acknowledgement message toremote network device 206 using the second communication protocol,indicating that remote network device 206 has been successfullyregistered with bridge 204. The acknowledgement message may comprise thereference code and/or other information indicating that remote networkdevice 206 has been registered with bridge 204. When remote networkdevice 206 receives the acknowledgement message from bridge 204, it maystore the reference code in a memory within remote network device 206.It may also automatically enter a “normal” mode of operation, e.g.,monitoring for a particular event and transmitting a status message tobridge 204 if the particular event occurs. Alternatively, or inaddition, it may provide a visual and/or audible alert to a user that ithas been registered with bridge 204. Subsequent transmissions fromremote network device 206 may include the reference code to identifyremote network device 206, in this case reference code “1”.

After remote network device 206 has successfully registered with bridge204, an audible or visual indication may be presented by bridge 204 to auser to signify the registration. Typically, information regarding theregistration may be accessible to a user via a user interface 304located on bridge 204. For example, after a successful registration, anLED may be illuminated for a predetermined time period and a user may beable to view the identification information stored within memory 302.Frequently, the user may add further information pertaining to eachdevice registered with bridge 204, such as a location of a remotenetwork device (e.g., “front door”, “window in living room”, “garagedoor”, etc). After successful device registration, bridge 204 and/orremote network device 206 are typically returned to a “normal” mode ofoperation, either automatically, after a predetermined time period, orby a user of system 200.

At some time later, the identification information stored in memory 302relating to remote network device 206 is provided to control device 202to complete the registration process. In one embodiment, identificationinformation related to other remote network devices that have registeredwith bridge 204 may be sent as well so that multiple remote networkdevices may be registered at one time. This process is shown beginningat block 420.

In one embodiment, at block 420, control device 202 is placed into learnmode once again.

At block 422, in one embodiment, bridge 204 automatically transmits oneor more registration information messages on behalf of remote networkdevice 206 to control device 202 using the first communication protocol.In one embodiment, the registration information message(s) normallycomprises a node identification code of bridge 204 that was assigned bycontrol device 202 at blocks 402-408. However, at block 422, when bridge204 transmits the registration information message on behalf of remotenetwork device 206, bridge 204 inserts a default node identificationcode indicating that registration has not yet occurred. Bridge 204 alsoinserts identification information into the registration informationmessage relating to remote network device 206. In essence, bridge 204masquerades as remote network device 206 attempting to register withcontrol device 202 for the first time.

In another embodiment, bridge 204 does not transmit one or moreregistration information messages at block 422 until after it has beenplaced into a fourth mode of operation (first mode being “normal” mode,second mode being “learn” mode, third being remote network device learnmode, described above), referred to herein as remote network deviceregistration mode. In yet another embodiment, bridge 204 does nottransmit a registration information message until it receives a messagefrom control device 202 requesting bridge 204 to provide such a message.

When control device 202 receives the registration information messagefrom bridge 204, it assigns a home identification code and/or a nodeidentification code to what control device 202 believes to be remotenetwork device 206, typically by creating a record in the electronicmemory within control device 202. The record typically comprises some orall of the identification information contained in the registrationinformation message, along with the just-assigned home identificationcode and the node identification code. Thus, remote network device 206is registered with control device 202 via bridge 204.

In one embodiment, after control device 202 has created the record inmemory and assigned a house identification code and/or nodeidentification code, it may automatically exit the learn mode, if it isrequired that control device 202 be placed in learn mode in order toregister devices. However, in another embodiment, control device 202 isable to process more than one registration information message beforeautomatically reverting to a normal mode of operation. Thus, in thisembodiment, control device may receive a registration informationmessage relating to a first remote network device that has previouslyregistered with bridge 204, and at some subsequent time, receive asecond information message relating to a second remote network devicethat has previously registered with bridge 204. This process maycontinue until all remote network devices that have previouslyregistered with bridge 204 have had their respective identificationinformation transmitted to control device 202. In one embodiment, bridge204 waits to receive an acknowledgement message transmitted by controldevice 202, indicating successful registration of any previousregistration information messages that were transmitted.

In one embodiment, control device 202 generates an acknowledgmentmessage that is received by bridge 204 indicating that registration wassuccessful at block 424. In another embodiment, this messageadditionally comprises the just-assigned home identification code and/orthe node identification code. In either case, the acknowledgementmessage conforms to the first communication protocol.

After remote network device 206 has successfully registered with controldevice 202, an audible or visual indication may be presented to a userto signify the registration, the indication presented by either controldevice 202, bridge 204, or both. Typically, information regarding theregistration may be accessible to a user via a display located on eitherbridge 204 or control device 202. For example, after a successfulregistration, an LED may be illuminated for a predetermined time periodon control device 202 and a user may be able to view the identificationinformation, home identification code, and/or node identification codeassociated with each registered network control device registered withcontrol device 202. Frequently, the user may add further informationpertaining to each device registered with control device 202, such as alocation of a remote network device (e.g., “front door”, “window inliving room”, “garage door”, etc). After successful device registration,bridge 204 and control device 202 are typically returned to a “normal”mode of operation, either automatically, after a predetermined timeperiod, or by a user of system 200.

In one embodiment, shown as block 426, bridge 204 stores the homeidentification code and/or node identification code contained within theacknowledgment message received at block 424 in memory 302 andassociates the home identification code and/or node identification codewith remote network device 206. The association of the homeidentification code and/or node identification code with remote networkdevice 206 may be referred to as the creation of a “virtual node,” andenables messages destined for remote network device 206, received bybridge 204 using the second communication protocol, to be correctlyaddressed to remote network device 206 using the second communicationprotocol.

In one embodiment, the home identification code and/or nodeidentification code provided by control device 202 is associated withthe reference code assigned to remote network device 206 by bridge 204at block 416. For example, if control device 202 assigned a nodeidentification code of “14” to bridge 204 after receiving theregistration information message from bridge 204 at block 422, bridge204 stores the node identification code (“14”) in memory 302 inassociation with the reference code (“1”) that bridge 204 assigned toremote network device 206 at block 416. Then, when a subsequent messageis received by bridge 204 from control device 202, addressed to node 14(i.e., remote network device 206), bridge 204 looks up a record inmemory 302 associated with node identification code 14 and determinesfrom the record that node identification code 14 corresponds to remotenetwork device 206, identified in the record as reference code “1”.Bridge 204 then re-transmits the message using the second communicationprotocol, addressing remote network device 206 using reference code “1”.

In another embodiment, where a reference code is not used, the homeidentification code and/or node identification code received at block516 is associated with remote network device 206 by storing the homeidentification code and/or node identification code in the recordassociated with remote network device 206. Then, when a subsequentmessage is received by bridge 204 from control device 202, addressed tonode 14 (i.e., remote network device 206), bridge 204 looks up a recordin memory 302 associated with node identification code 14 and determinesfrom the record that node identification code 14 corresponds to remotenetwork device 206, identified in the record by information such as aserial number associated with remote network device 206. Bridge 204 thenre-transmits the message from control device 202 using the secondcommunication protocol, addressing remote network device 206 using theserial number associated in the record with node 14.

FIGS. 5a-5c are flow diagrams illustrating another embodiment of amethod 500 for allowing a remote network device to register with controldevice 202 when control device 202 and the remote network device operateusing disparate communication protocols. It should be understood that insome embodiments, not all of the steps shown in FIG. 5 are performed. Itshould also be understood that the order in which the steps are carriedout may be different in other embodiments.

At block 502, control device 202 is placed into a “learn” mode ofoperation from a “normal” mode of operation typically by pressing one ormore pushbuttons on control device 202. In the learn mode of operation,control device may accept registration information messages from remotenetwork devices and, in response, register, or add them, as afunctioning unit within network 200. In the normal mode of operation,control device typically receives status messages from remote networkdevices (e.g., door/window open/closed, motion detected, audio and/orvideo data, “tile” information, etc) and/or transmits messages to theremote network devices instructing one or more of them to perform anaction, such as determine a status of the remote network device, performa survey of other remote network devices within range of a remotenetwork device, transmit a status of a remote network device, etc.

In one embodiment, in response to being placed into learn mode, controldevice 202 transmits a message requesting that any device that has notbeen previously registered with control device 202 to respond to themessage. In another embodiment, the message instructs any device,registered or not, to respond to the message. In either case, themessage is transmitted using a first communication protocol.

At block 504, bridge 204 may also be placed into a “learn” mode ofoperation from a “normal” mode of operation typically by pressing one ormore pushbuttons on bridge 204. In the learn mode of operation, bridge204 accepts registration information messages from remote networkdevices using a first communication protocol and stores informationcontained in the registration information messages so that the remotenetwork devices may be accessible to control device 202, as describedbelow. In another embodiment, bridge 204 helps to register remotenetwork devices automatically without having to be placed into a learnmode by a user.

In one embodiment, in response to being placed into learn mode, bridge204 transmits a message using a first communication protocol, requestingthat any remote network device that has not been previously registeredwith bridge 204 to respond to the message. In another embodiment, themessage instructs any device, registered or not, to respond to themessage. In either case, the message is transmitted using a firstcommunication protocol common to both bridge 204 and one or more remotenetwork devices. In response to receiving the message, one or moreremote network devices responds by transmitting a registrationinformation message using the first communication protocol. In thepresent example, remote network device 206 has not yet been registeredwith bridge 204. The registration information message typicallycomprises identification information pertaining to remote network device206, such as a pre-assigned serial number, a device type (such as abasic device type, a specific device type, a generic device type, etc.),and/or a device status (e.g., open, closed, temperature, on, off, etc).The identification information may also comprise other information aswell, such as the capabilities of remote network device 206, forexample, whether remote network device 206 is capable of repeatingmessages to other network devices, whether remote network device 206 iscapable of continually “listening” for incoming messages, etc.

At block 506, bridge 204 receives a registration information messagefrom a remote network device, such as remote network device 206 (in thisexample, remote network device 206 comprises a window sensor) using afirst communication protocol common to remote network device 206 andbridge 204, such as the well-known Zigbee® communication protocol. Theregistration information message need not be used exclusively for deviceregistration. For example, in a Z-wave-based network, messagestransmitted by remote network devices comprises a home identificationcode and a node identification code if a device has been previouslyregistered, or “included”, with control device 202. Unregistered devicesdo not transmit a home identification code or node identification code,or, in another embodiment, a default home and/or node identificationcode is used that is recognized by control device 202 as a default codeused by unregistered devices. Thus, receipt of a registrationinformation message, such as a “node information frame”, that does notinclude a pre-assigned home identification code and/or nodeidentification code may be considered a registration information messageby control device 202 or bridge 204.

In any case, the registration information message typically comprisesidentification information, typically a pre-assigned serial number, adevice type (such as a basic device type, a specific device type, ageneric device type, etc.), and/or a device status (e.g., open, closed,temperature, on, off, tilt information, etc). The identificationinformation may also comprise other information as well, such as thecapabilities of remote network device 206, for example, whether remotenetwork device 206 is capable of repeating messages to other networkdevices, whether remote network device 206 is capable of continually“listening” for incoming messages, a list of other remote networkdevices in range of remote network device 206, etc.

At block 508, processor 300 inside bridge 204 creates a record in memory302. The record comprises at least some of the identificationinformation in the registration information message. In addition,processor 300 may assign a reference code to remote network device 206and associate the reference code with remote network device 206, e.g.,the identification information stored in the record inside memory 302,as shown at block 510. The reference code may be used by processor 300to identify remote network devices that have “registered” with bridge204, e.g., have had a record created in memory 302. For example, thereference code may comprise one of a series of alpha-numeric codes. Forpurposes of example, it is assumed that remote network device 206 is thefirst device to register with bridge 204 and is assigned a referencecode equal to “1”.

At block 512, bridge 204 may transmit an acknowledgement message toremote network device 206 using the first communication protocol,indicating that remote network device 206 has been successfullyregistered with bridge 204. In another embodiment, no acknowledgmentmessage is transmitted (some remote network devices do not have thecapability to receive messages). The acknowledge message may comprisethe reference code and/or other information (e.g., the time ofregistration) indicating that remote network device 206 has beenregistered with bridge 204. When remote network device 206 receives theacknowledgement message from bridge 204, it may store the reference codein a memory within remote network device 206. It may also automaticallyenter a “normal” mode of operation, e.g., monitoring for a particularevent and transmitting a status message to bridge 204 if the particularevent occurs. Alternatively, or in addition, it may provide a visualand/or audible alert to a user that it has been registered with bridge204. Subsequent transmissions from remote network device 206 may includethe reference code to identify remote network device 206, in this casereference code “1”.

At some time after block 512, bridge 204 transmits a registrationinformation message on behalf of remote network device 206 to controldevice 202 using a second communication protocol that is common tobridge 204 and control device 202, such as the well-known Z-wave®communication protocol. This is shown as block 514. Many communicationprotocols, including the Z-wave® protocol, comprise rules forregistering remote network devices with control device 202. For example,in order for a Z-wave compatible remote network device to register witha Z-wave compatible control device 202, the remote network devicetransmits a “node information frame”, which is a message that comprisesidentifying characteristics of the particular remote network device,such as a per-assigned serial number, device type, device status, etc.The node information frame may be repeated for any number of times andmay terminate when, for example, an acknowledgement message is receivedfrom control device 202 or bridge 204, as the case may be. When receivedby control device 202 while in a learn mode of operation, the remotenetwork device is registered with, or “included”, into control device202, thereby allowing it to become an operational node within a networkof remote network devices managed by control device 202.

The registration information message transmitted by bridge 204 at block514 typically comprises a pre-assigned serial number of remote networkdevice 206 and an indication of a remote network device 206 type. Theregistration information message may also comprise an indication of thestatus of remote network device 206 and/or capabilities of remotenetwork device 206. Thus, bridge 204, in essence, masquerades as remotenetwork device 206.

In response to receiving the registration information message, controldevice 202 adds remote network device 206 as a functioning “node” innetwork 200 by assigning a home identification code and/or a nodeidentification code to bridge 204, believing that bridge 204 is remotenetwork device 206 (as the registration information message received bycontrol device 202 identifies remote network device 206). A record iscreated by control device 202, associating the home identification codeand/or node identification code with remote network device 206.Subsequent messages transmitted from control device 202 to remotenetwork device 206 comprise the assigned home identification code and/ornode identification code as a way to target, or address, remote networkdevice 206.

After network control device 206 has been registered with control device202, control device 202 may transmit an acknowledgement message back tobridge 204 using the second communication protocol, the acknowledgementmessage typically comprising the just-assigned home identification codeand/or node identification code as an indication that remote networkdevice 206 has been successfully registered with control device 202.

At block 516, bridge 204 receives the acknowledgement messagetransmitted by control device 202 using the second communicationprotocol. In response, in one embodiment shown at block 518, bridge 204stores the home identification code and/or node identification codecontained within the acknowledgment message in memory 302 and associatesthe home identification code and/or node identification code with remotenetwork device 206, as shown in block 520. The association of the homeidentification code and/or node identification code with remote networkdevice 206 may be referred to as the creation of a “virtual node,” andenables messages destined for remote network device 206, received bybridge 204 using the second communication protocol, to be correctlyaddressed to remote network device 206 using the first communicationprotocol. In one embodiment, the home identification code and/or nodeidentification code provided by control device 202 is associated withthe reference code assigned to remote network device 206 by bridge 204at block 510. For example, if control device 202 assigned a nodeidentification code of “23” to bridge 204 after receiving theregistration information message from bridge 204 at block 514, bridge204 stores the node identification code (“23”) in memory 302 inassociation with the reference code (“1”) that bridge 204 assigned toremote network device 206 at block 510. Then, when a subsequent messageis received by bridge 204 from control device 202, addressed to node 23(i.e., remote network device 206), bridge 204 looks up a record inmemory 302 associated with node identification code 23 and determinesfrom the record that node identification code 23 corresponds to remotenetwork device 206, identified in the record as reference code “1”.Bridge 204 then re-transmits the message using the first communicationprotocol, addressing remote network device 206 using reference code “1”.

In another embodiment, where a reference code is not used, the homeidentification code and/or node identification code received at block516 is associated with remote network device 206 by storing the homeidentification code and/or node identification code in the recordassociated with remote network device 206. Then, when a subsequentmessage is received by bridge 204 from control device 202, addressed tonode 23 (i.e., remote network device 206), bridge 204 looks up a recordin memory 302 associated with node identification code 23 and determinesfrom the record that node identification code 23 corresponds to remotenetwork device 206, identified in the record by information such as aserial number associated with remote network device 206. Bridge 204 thenre-transmits the message from control device 202 using the firstcommunication protocol, addressing remote network device 206 using theserial number associated in the record with node 23.

At block 522, bridge 204 may reset the home identification code and/ornode identification code of bridge 204. In some embodiments, the homeidentification code and/or node identification code received by bridge204 at block 516 is stored in memory 302 and, either additionally oralternatively, associated with bridge 204, in accordance with, forexample, the second communication protocol. Thus, at block 522, bridge204 may reset the home identification code and/or node identificationcode associated with bridge 204 by, in one embodiment, erasing the homeidentification code and/or node identification code in memory 302. Inanother embodiment, a default home identification code and/or nodeidentification code replaces the home identification code and/or nodeidentification code in memory 302 that was previously associated withbridge 204. In yet another embodiment, the home identification codeand/or node identification code remains stored in memory, but isdis-associated with bridge 204. In other words, while the homeidentification code and/or node identification code remains stored inmemory (and associated with remote network device 206), bridge 204ignores this information and does not include the home identificationcode and/or node identification code in subsequent transmissions.

At block 524, bridge 204 receives a registration information messagefrom a second remote network device, for example remote network device208 (in this example, remote network device 208 comprises a doorsensor), using a third communication protocol common to the remotenetwork device 208 and bridge 204. The third communication protocol maybe the same as the first communication protocol or it may be different.

As noted previously, the registration information message received fromremote network device 208 typically comprises identificationinformation, typically a pre-assigned serial number, a device type (suchas a basic device type, a specific device type, a generic device type,etc.), and/or a device status (e.g., open, closed, temperature, on, off,tilt information, etc). The identification information may also compriseother information as well, such as the capabilities of remote networkdevice 208, for example, whether remote network device 208 is capable ofrepeating messages to other network devices, whether remote networkdevice 208 is capable of continually “listening” for incoming messages,a list of other remote network devices in range of remote network device208, etc.

At block 526, processor 300 inside bridge 204 creates a second record inmemory 302. The second record comprises at least some of theidentification information in the registration information message fromremote network device 208. In addition, processor 300 may assign asecond reference code to remote network device 208, different than theone assigned to remote network device 206, and associate the secondreference code with remote network device 208, e.g., the identificationinformation stored in the second record inside memory 302, at block 528.For purposes of this example, it is assumed that remote network device208 is the second device to register with bridge 204 and is assigned areference code equal to “2”.

At block 530, bridge 204 may transmit an acknowledgement message toremote network device 208 using the third communication protocol,indicating that remote network device 208 has been successfullyregistered with bridge 204. The acknowledge message may comprise thereference code and/or other information indicating that remote networkdevice 208 has been registered with bridge 204. In another embodiment,an acknowledgement message is sent to remote network device 208 onlyafter it has been successfully registered with control device 202. Whenremote network device 208 receives the acknowledgement message frombridge 204, it may store the reference code in a memory within remotenetwork device 208. It may also automatically enter a “normal” mode ofoperation, e.g., monitoring for a particular event and transmitting astatus message to bridge 204 if the particular event occurs.Alternatively, or in addition, it may provide a visual and/or audiblealert to a user that it has been registered with bridge 204. Subsequenttransmissions from remote network device 208 may include the referencecode to identify remote network device 208, in this case reference code“2”.

At some time after block 530, bridge 204 transmits a registrationinformation message on behalf of remote network device 208 to controldevice 202 using a second communication protocol that is common tobridge 204 and control device 202, such as the well-known Z-wave®communication protocol. This is shown as block 532.

The registration information message transmitted by bridge 204 at block530 typically comprises a pre-assigned serial number of remote networkdevice 208 and an indication of a remote network device 208 type. Theregistration information message may also comprise an indication of thestatus of remote network device 208 and/or capabilities of remotenetwork device 208.

In response to receiving the registration information message, controldevice 202 adds remote network device 208 as a functioning “node” innetwork 200 by assigning a home identification code and/or a nodeidentification code to bridge 204, believing that bridge 204 is remotenetwork device 208 (as the registration information message received bycontrol device 202 identifies remote network device 208). A secondrecord is created by control device 202, associating the homeidentification code and/or node identification code with remote networkdevice 208, e.g., the information contained in the registrationinformation message. Subsequent messages transmitted from control device202 to remote network device 208 typically comprise the assigned homeidentification code and/or node identification code as a way to target,or address, remote network device 208.

After network control device 208 has been registered with control device202, control device 202 may transmit an acknowledgement message back tobridge 204 using the second communication protocol, the acknowledgementmessage typically comprising the just-assigned home identification codeand/or node identification code as an indication that remote networkdevice 208 has been successfully registered with control device 202.

At block 534, bridge 204 receives the acknowledgement messagetransmitted by control device 202 using the second communicationprotocol. In response, in one embodiment shown at block 534, bridge 204stores the home identification code and/or node identification codecontained within the acknowledgment message in memory 302 and associatesthe home identification code and/or node identification code with remotenetwork device 208, as shown in blocks 536 and 538. The association ofthe home identification code and/or node identification code with remotenetwork device 208 may be referred to as the creation of a “virtualnode,” and enables messages destined for remote network device 208,received by bridge 204 using the second communication protocol, to becorrectly addressed to remote network device 208 using the thirdcommunication protocol. In one embodiment, the home identification codeand/or node identification code provided by control device 202 isassociated with the reference code assigned to remote network device 208by bridge 204 at block 538. For example, if control device 202 assigneda node identification code of “24” to bridge 204 after receiving theregistration information message from bridge 204 at block 532, bridge204 stores the node identification code (“24”) in memory 302 inassociation with the reference code that bridge 204 assigned to remotenetwork device 208 at block 528 (“2”). Then, when a subsequent messageis received by bridge 204 from control device 202, addressed to node 24(i.e., remote network device 208), bridge 204 looks up a record inmemory 302 associated with node identification code 24 and determinesfrom the record that node identification code 24 corresponds to remotenetwork device 208, identified in the record as reference code “2”.Bridge 204 then re-transmits the message using the third communicationprotocol, addressing remote network device 208 using reference code “2”.

In another embodiment, where a reference code is not used, the homeidentification code and/or node identification code received at block524 is associated with remote network device 208 by storing the homeidentification code and/or node identification code in the recordassociated with remote network device 208. Then, when a subsequentmessage is received by bridge 204 from control device 202, addressed tonode 24 (i.e., remote network device 208), bridge 204 looks up a recordin memory 302 associated with node identification code 24 and determinesfrom the record that node identification code 24 corresponds to remotenetwork device 208, identified in the record by information such as aserial number associated with remote network device 208. Bridge 204 thenre-transmits the message from control device 202 using the thirdcommunication protocol, addressing remote network device 206 using theserial number associated in the record with node 24.

At block 540, bridge 204 may reset the home identification code and/ornode identification code of bridge 204. In some embodiments, the homeidentification code and/or node identification code received by bridge204 at block 534 is stored in memory 302 and, either additionally oralternatively, associated with bridge 204, in accordance with one ormore communication protocols in use today. Thus, at block 540, bridge204 may reset the home identification code and/or node identificationcode associated with bridge 204 by, in one embodiment, erasing the homeidentification code and/or node identification code in memory 302. Inanother embodiment, a default home identification code and/or nodeidentification code replaces the home identification code and/or nodeidentification code in memory 302 that was previously associated withbridge 204. In yet another embodiment, the home identification codeand/or node identification code remains stored in memory, but isdis-associated with bridge 204. In other words, while the homeidentification code and/or node identification code remains stored inmemory (and associated with remote network device 208), bridge 204ignores this information and does not include the home identificationcode and/or node identification code in subsequent transmissions.

The methods or algorithms described in connection with the embodimentsdisclosed herein may be embodied directly in hardware or embodied inprocessor-readable instructions executed by a processor. Theprocessor-readable instructions may reside in RAM memory, flash memory,ROM memory, EPROM memory, EEPROM memory, registers, hard disk, aremovable disk, a CD-ROM, or any other form of storage medium known inthe art. An exemplary storage medium is coupled to the processor suchthat the processor can read information from, and write information to,the storage medium. In the alternative, the storage medium may beintegral to the processor. The processor and the storage medium mayreside in an ASIC. The ASIC may reside in a user terminal. In thealternative, the processor and the storage medium may reside as discretecomponents.

Accordingly, an embodiment of the invention may comprise anon-transitory processor-readable media embodying code orprocessor-readable instructions to implement the teachings, methods,processes, algorithms, steps and/or functions disclosed herein.

While the foregoing disclosure shows illustrative embodiments of theinvention, it should be noted that various changes and modificationscould be made herein without departing from the scope of the inventionas defined by the appended claims. The functions, steps and/or actionsof the method claims in accordance with the embodiments of the inventiondescribed herein need not be performed in any particular order.Furthermore, although elements of the invention may be described orclaimed in the singular, the plural is contemplated unless limitation tothe singular is explicitly stated.

We claim:
 1. A method implemented by a bridge device for registering aremote network device with a control device, wherein the remote networkdevice communicates using a first communication protocol and the controldevice communicates using a second communication protocol, the methodcomprising: receiving a registration information message from the remotenetwork device using the first communication protocol, the registrationinformation message comprising identification information relating tothe remote network device; creating a record within a memory, the recordfor storing at least some of the identification information;transmitting a second registration information message to the controldevice using the second communication protocol, the second registrationinformation message comprising at least some of the identificationinformation; receiving an acknowledgement message from the controldevice using the second communication protocol, the acknowledgementmessage comprising an identification code assigned by the controldevice, the identification code uniquely identifying the remote networkdevice; storing the identification code in the memory; associating theidentification code with the identification information; receiving asubsequent message from the remote network device, the subsequentmessage comprising the identification information; determining that theidentification information is associated with the identification code;and re-transmitting the subsequent message to the control device, there-transmitted subsequent message comprising the identification code. 2.The method of claim 1, further comprising: setting a bridge deviceidentification code to the identification code in the memory; resettingthe bridge device identification code prior to transmission of a thirdregistration information message to the control device.
 3. The method ofclaim 2, wherein resetting the bridge device identification codecomprises erasing the bridge device identification code from the memory.4. The method of claim 2, wherein resetting the bridge deviceidentification code comprises replacing the bridge device identificationcode with a default identification code.
 5. The method of claim 2,wherein resetting the bridge device identification code comprisestransmitting the third registration information message without thebridge device identification code.
 6. The method of claim 1, furthercomprising: transmitting an acknowledgment message to the remote networkdevice using the first communication protocol, the acknowledgmentmessage comprising the identification code; and re-transmitting thesubsequent message to the remote network device using the identificationcode to address the remote network device.
 7. The method of claim 1,further comprising: receiving a third registration information messagefrom a second remote network device using a third communication protocolcommon to the second network device and the bridge device, the thirdregistration information message comprising identification informationrelating to the second remote network device; creating a record in thememory for storing at least some of the identification information fromthe third registration information message; transmitting a fourthregistration information message to the control device using the secondcommunication protocol, the fourth registration information messagecomprising at least some of the identification information relating tothe second remote network device; receiving a second acknowledgementmessage from the control device using the second communication protocol,the acknowledgement message comprising a second identification codeassigned by the control device, the second identification code uniquelyidentifying the second remote network device; storing the secondidentification code in the memory; associating the second identificationcode with the identification information from the second remote networkdevice; receiving a second subsequent message from the second remotenetwork device, the second subsequent message comprising theidentification information relating to the second remote network device;determining that at least some of the identification information in thesubsequent message is associated with the second identification code;and re-transmitting the subsequent message to the control device, there-transmitted subsequent message comprising the second identificationcode.
 8. An apparatus for registering a remote network device with acontrol device, wherein the remote network device communicates using afirst communication protocol and the control device communicates using asecond communication protocol, the apparatus comprising: a firsttransceiver for communicating with the remote network device using thefirst communication protocol; a second transceiver for communicatingwith the control device using the second communication protocol; aprocessor for executing processor-executable instructions; and a memoryfor storing the processor-executable instructions, theprocessor-executable instructions causing the apparatus to: receive aregistration information message from an unregistered remote networkdevice using the first communication protocol, the registrationinformation message comprising identification information relating tothe unregistered remote network device; create a record within a memory,the record for storing at least some of the identification information;transmit a second registration information message to the control deviceusing the second communication protocol, the second registrationinformation message comprising at least some of the identificationinformation; receive an acknowledgement message from the control deviceusing the second communication protocol, the acknowledgement messagecomprising an identification code assigned by the control device, theidentification code uniquely identifying the remote network device;store the identification code in the memory; associate theidentification code with the identification information; receive asubsequent message from the remote network device, the subsequentmessage comprising the identification information; determine that theidentification information is associated with the identification code;and re-transmit the subsequent message to the control device, there-transmitted subsequent message comprising the identification code. 9.The apparatus of claim 8, wherein the processor-executable instructionsfurther comprises instructions that cause the apparatus to: set a bridgedevice identification code to the identification code in the memory;reset the bridge device identification code prior to transmission of athird registration information message by the bridge device.
 10. Theapparatus of claim 9, wherein resetting the bridge device identificationcode comprises erasing the bridge device identification code from thememory.
 11. The apparatus of claim 9, wherein resetting the bridgedevice identification code comprises replacing the bridge deviceidentification code with a default identification code.
 12. Theapparatus of claim 9, wherein resetting the bridge device identificationcode comprises transmitting the third registration information messagethat lacks the identification code.
 13. The apparatus of claim 8,wherein the processor-executable instructions further comprisinginstructions that cause the apparatus to: transmit an acknowledgmentmessage to the remote network device using the first communicationprotocol, the acknowledgment message comprising the identification code;and re-transmit the subsequent message to the remote network deviceusing the identification code to address the remote network device. 14.The apparatus of claim 8, wherein the processor-executable instructionsfurther comprising instructions that cause the apparatus to: receive athird registration information message from a second remote networkdevice using a third communication protocol common to the second networkdevice and the bridge device, the third registration information messagecomprising identification information relating to the second remotenetwork device; create a record in the memory for storing at least someof the identification information from the third registrationinformation message; transmit a fourth registration information messageto the control device using the second communication protocol, thefourth registration information message comprising at least some of theidentification information relating to the second remote network device;receive a second acknowledgement message from the control device usingthe second communication protocol, the acknowledgement messagecomprising a second identification code assigned by the control device,the second identification code uniquely identifying the second remotenetwork device; store the second identification code in the memory;associate the second identification code with the identificationinformation from the second remote network device; receive a secondsubsequent message from the second remote network device, the secondsubsequent message from the second remote network device comprising theidentification information from the second remote network device;determine that at least some of the identification information in thesecond subsequent message from the second remote network device isassociated with the second identification code; and re-transmit thesecond subsequent message to the control device, the re-transmittedsecond subsequent message comprising the second identification code. 15.The method of claim 1, further comprising: providing an alert to a userindicating that the remote network device has been registered with thecontrol device in response to receiving the acknowledgment message. 16.The apparatus of claim 8, further comprising: a user interface forproviding an alert to a user indicating that the remote network devicehas been registered with the control device in response to receiving theacknowledgment message.